New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom naming for multi output primitives #780
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think GroupByTransformFeature should also implement generate_names
f = 'MULTI_CUM_SUM(age) by région_id[%d]' % i | ||
f = 'MULTI_CUM_SUM(age)[%d] by région_id' % i | ||
assert f in fm.columns | ||
for x, y in zip(fm[f].values, correct_answers[i][1].values): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this test, can we also calculate the standard groupby features in a separate DFS call and compare, to see if the multioutput code path alters any values?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Pull Request Description
Updates to allow for custom naming of multioutput primitives. Implements a
generate_names
method inPrimitiveBase
class that can be overridden when creating a custom primitive.This change was discussed in Issues #591 and #593.